Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea7e0fc732509885e0710bba52a15fe15a08a5bb08f9f156600d60c67f274c98

Tx prefix hash: 5fb7083a61c1e56fde200c9d80a1353463adc01f7c4e153d8d6c41a88e39d8fb
Tx public key: 70b623412a680314e33becb1224f6d713cd45e446a7df72fdf0d24c5cf0e5fea
Timestamp: 1609181302 Timestamp [UCT]: 2020-12-28 18:48:22 Age [y:d:h:m:s]: 03:333:00:54:58
Block: 171005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 990608 RingCT/type: yes/0
Extra: 0170b623412a680314e33becb1224f6d713cd45e446a7df72fdf0d24c5cf0e5fea02110000042bdf1e48bb000000000000000000

1 output(s) for total of 166.490750790000 dcy

stealth address amount amount idx
00: fed0f0de66302cca217559dc47eba3d37db4512b8d1c613811da9e1becadf2e8 166.490750790000 321440 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": 171015, "vin": [ { "gen": { "height": 171005 } } ], "vout": [ { "amount": 166490750790, "target": { "key": "fed0f0de66302cca217559dc47eba3d37db4512b8d1c613811da9e1becadf2e8" } } ], "extra": [ 1, 112, 182, 35, 65, 42, 104, 3, 20, 227, 59, 236, 177, 34, 79, 109, 113, 60, 212, 94, 68, 106, 125, 247, 47, 223, 13, 36, 197, 207, 14, 95, 234, 2, 17, 0, 0, 4, 43, 223, 30, 72, 187, 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