Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35d998065074c731ba70715a618246126ac22a291b7b51f343f8e8fc2e740736

Tx prefix hash: 570dde6a0194f1eaed580ddd192a2b71d1818d051b3564d752448eea6c31fa8e
Tx public key: 3e8a0834a375ce3a426ad62de98102dc3ab3b051f0a4daf6725b5f4c881e6299
Timestamp: 1674191021 Timestamp [UCT]: 2023-01-20 05:03:41 Age [y:d:h:m:s]: 02:291:22:47:18
Block: 678644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 728025 RingCT/type: yes/0
Extra: 013e8a0834a375ce3a426ad62de98102dc3ab3b051f0a4daf6725b5f4c881e62990211000000025029cbac000000000000000000

1 output(s) for total of 3.462347501000 dcy

stealth address amount amount idx
00: e13fe9efe2ab87e0682aa62eb04b2155b7062ccb28c74157e1eab33541f74689 3.462347501000 1120535 of 0

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": 678654, "vin": [ { "gen": { "height": 678644 } } ], "vout": [ { "amount": 3462347501, "target": { "key": "e13fe9efe2ab87e0682aa62eb04b2155b7062ccb28c74157e1eab33541f74689" } } ], "extra": [ 1, 62, 138, 8, 52, 163, 117, 206, 58, 66, 106, 214, 45, 233, 129, 2, 220, 58, 179, 176, 81, 240, 164, 218, 246, 114, 91, 95, 76, 136, 30, 98, 153, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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