Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49dfcbd28fe993a1cca6cf4eb7adb137742360c9a9e137ef4ae766422ed80a0e

Tx prefix hash: f68ee05e1673b5fa3d8dc1ae00cb7d7de2d96deaf7fdc6e4432ea457065c8fa8
Tx public key: 602b0454ee8b6ba0f4ba38c0dbca38c5fb8b27e0c6c8c88e66b4ebf6c83a24f8
Timestamp: 1721008945 Timestamp [UCT]: 2024-07-15 02:02:25 Age [y:d:h:m:s]: 00:266:01:22:31
Block: 1065934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190050 RingCT/type: yes/0
Extra: 01602b0454ee8b6ba0f4ba38c0dbca38c5fb8b27e0c6c8c88e66b4ebf6c83a24f802110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63c253008d384e603522d41dcf4fcdb6e14db65f123b2ebc7a4ed4d97c349760 0.600000000000 1536503 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": 1065944, "vin": [ { "gen": { "height": 1065934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63c253008d384e603522d41dcf4fcdb6e14db65f123b2ebc7a4ed4d97c349760" } } ], "extra": [ 1, 96, 43, 4, 84, 238, 139, 107, 160, 244, 186, 56, 192, 219, 202, 56, 197, 251, 139, 39, 224, 198, 200, 200, 142, 102, 180, 235, 246, 200, 58, 36, 248, 2, 17, 0, 0, 0, 13, 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