Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da880efef194049f0f512f16dbde67838fa5a6586bfaddf54a0f29fa201026dc

Tx prefix hash: 784d2e084d1d2bbf0425433a403e8ee30fcfaafa47a36a98888c03c5c9ef6e1d
Tx public key: cd907ee215a6c9ed9fdb3cd1356b7b4268d9bd31ccdf8c5ee785535f1ea52dbc
Timestamp: 1728366077 Timestamp [UCT]: 2024-10-08 05:41:17 Age [y:d:h:m:s]: 00:198:23:21:29
Block: 1126913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142014 RingCT/type: yes/0
Extra: 01cd907ee215a6c9ed9fdb3cd1356b7b4268d9bd31ccdf8c5ee785535f1ea52dbc021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cbdfb9db2603d2efee7ba8003717ad6cad3f1a7f5a08403827b481898566556 0.600000000000 1609712 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": 1126923, "vin": [ { "gen": { "height": 1126913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cbdfb9db2603d2efee7ba8003717ad6cad3f1a7f5a08403827b481898566556" } } ], "extra": [ 1, 205, 144, 126, 226, 21, 166, 201, 237, 159, 219, 60, 209, 53, 107, 123, 66, 104, 217, 189, 49, 204, 223, 140, 94, 231, 133, 83, 95, 30, 165, 45, 188, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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