Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57d0c682a74c75c01254e12046892b6a38e0c4e4e2cc3d385044dc6f537454d7

Tx prefix hash: 8332fd761f500814c042d6593132b3389d2f78cfe67b7cda673b11e9226b0b14
Tx public key: 790dc312460cec4fb0980d2177d3fd3acd37d892f2569675fc20369a523652e4
Timestamp: 1735664629 Timestamp [UCT]: 2024-12-31 17:03:49 Age [y:d:h:m:s]: 00:350:21:32:36
Block: 1187282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248350 RingCT/type: yes/0
Extra: 01790dc312460cec4fb0980d2177d3fd3acd37d892f2569675fc20369a523652e4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32f5aab80538f1a2112d16089b92a812b9fa8122e024ad617cae98b19ecf652e 0.600000000000 1673771 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": 1187292, "vin": [ { "gen": { "height": 1187282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32f5aab80538f1a2112d16089b92a812b9fa8122e024ad617cae98b19ecf652e" } } ], "extra": [ 1, 121, 13, 195, 18, 70, 12, 236, 79, 176, 152, 13, 33, 119, 211, 253, 58, 205, 55, 216, 146, 242, 86, 150, 117, 252, 32, 54, 154, 82, 54, 82, 228, 2, 17, 0, 0, 0, 2, 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