Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ffc59f802907d4ad5cf9853aedb577e0b9696a7c7a8e8f01dfd879f4c27d9a2

Tx prefix hash: 1c6292a4479e01e8ed162244d0f6016f24e0208906eff135ba2b739ff0967454
Tx public key: 7eea4c09000cceeb5410fbe71668cf25f17b7bba27c6ee6568cfa58c4f22ab8c
Timestamp: 1578670015 Timestamp [UCT]: 2020-01-10 15:26:55 Age [y:d:h:m:s]: 05:296:08:08:14
Block: 42807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1359452 RingCT/type: yes/0
Extra: 017eea4c09000cceeb5410fbe71668cf25f17b7bba27c6ee6568cfa58c4f22ab8c02110000000117786bcf000000000000000000

1 output(s) for total of 442.755008303000 dcy

stealth address amount amount idx
00: 1f0cb61d4aace0715757a8e190dd294bf9258552d54fb6fdb9d1681274b814d2 442.755008303000 77234 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": 42817, "vin": [ { "gen": { "height": 42807 } } ], "vout": [ { "amount": 442755008303, "target": { "key": "1f0cb61d4aace0715757a8e190dd294bf9258552d54fb6fdb9d1681274b814d2" } } ], "extra": [ 1, 126, 234, 76, 9, 0, 12, 206, 235, 84, 16, 251, 231, 22, 104, 207, 37, 241, 123, 123, 186, 39, 198, 238, 101, 104, 207, 165, 140, 79, 34, 171, 140, 2, 17, 0, 0, 0, 1, 23, 120, 107, 207, 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