Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76984e8a9fc0b089c287333ec0ff61ee87126ff0dff0a2078d46653d6eb4c4f9

Tx prefix hash: e8959b7f429e775cee7f331289a4c7a06037eb0d1f4055106874656b9e2e0ae3
Tx public key: 4f1f93faa2f8d8011524b126bac08232f6125e42bb65d3cc17b0a1a70ff4a7f8
Timestamp: 1732442968 Timestamp [UCT]: 2024-11-24 10:09:28 Age [y:d:h:m:s]: 00:354:21:35:37
Block: 1160610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251199 RingCT/type: yes/0
Extra: 014f1f93faa2f8d8011524b126bac08232f6125e42bb65d3cc17b0a1a70ff4a7f8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1606ba87559b709293b9837eb6fe0e2849031848306d05774cc7bf72b0cd11a 0.600000000000 1646257 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": 1160620, "vin": [ { "gen": { "height": 1160610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1606ba87559b709293b9837eb6fe0e2849031848306d05774cc7bf72b0cd11a" } } ], "extra": [ 1, 79, 31, 147, 250, 162, 248, 216, 1, 21, 36, 177, 38, 186, 192, 130, 50, 246, 18, 94, 66, 187, 101, 211, 204, 23, 176, 161, 167, 15, 244, 167, 248, 2, 17, 0, 0, 0, 3, 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