Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1e9f7d156a1c3ff6d3c5b2aad1640c30d170952b938494c720ddee804dc9fb

Tx prefix hash: 63fb822e5b9b29f09b158659d4a16cb9b43859811927e314ad5930534521205e
Tx public key: 8b10ce4dbf984f358e5ee210f93ea30dc75bd23cf6bb21738fe38fcdc6acb22d
Timestamp: 1721718189 Timestamp [UCT]: 2024-07-23 07:03:09 Age [y:d:h:m:s]: 00:268:19:19:13
Block: 1071791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192041 RingCT/type: yes/0
Extra: 018b10ce4dbf984f358e5ee210f93ea30dc75bd23cf6bb21738fe38fcdc6acb22d02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51c3f5d30cb006dc5104b1fee61db1dec6f2a250fe08d76442a593ea736181c0 0.600000000000 1544150 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": 1071801, "vin": [ { "gen": { "height": 1071791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51c3f5d30cb006dc5104b1fee61db1dec6f2a250fe08d76442a593ea736181c0" } } ], "extra": [ 1, 139, 16, 206, 77, 191, 152, 79, 53, 142, 94, 226, 16, 249, 62, 163, 13, 199, 91, 210, 60, 246, 187, 33, 115, 143, 227, 143, 205, 198, 172, 178, 45, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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