Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e831b78102e8a2846e8671976a0fb4947d9185e2ddf2d4f187b25398450b3ff7

Tx prefix hash: f0eb564cad239fca36e4489fea0ea0c953cee5739ff43979e4d9bfa5231fbbaf
Tx public key: d3a3c4db60a1525a5c559b0561e9d58f504eae32dba9c7c7bf15e8911c508f80
Timestamp: 1730487577 Timestamp [UCT]: 2024-11-01 18:59:37 Age [y:d:h:m:s]: 00:141:06:48:02
Block: 1144412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100813 RingCT/type: yes/0
Extra: 01d3a3c4db60a1525a5c559b0561e9d58f504eae32dba9c7c7bf15e8911c508f80021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42f3bb27eab258028a9466ce8a5bc6452761ef4f29adde5579772529c592bac1 0.600000000000 1628625 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1144422, "vin": [ { "gen": { "height": 1144412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42f3bb27eab258028a9466ce8a5bc6452761ef4f29adde5579772529c592bac1" } } ], "extra": [ 1, 211, 163, 196, 219, 96, 161, 82, 90, 92, 85, 155, 5, 97, 233, 213, 143, 80, 78, 174, 50, 219, 169, 199, 199, 191, 21, 232, 145, 28, 80, 143, 128, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8