Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb94eb8c2cdddd8b0c8f46d1d99beec812bc8e884615340e465f3f8a04c1d671

Tx prefix hash: 0c672d8f7694d5e87acd6aae0beb5a6e9daa1c98a348e1367bb1a945c9f7dc73
Tx public key: 78f80bfdd17458ab847ba20c5ff2f5fbe6e7e4f0e44eeef8bab185ce4bf24e11
Timestamp: 1583753495 Timestamp [UCT]: 2020-03-09 11:31:35 Age [y:d:h:m:s]: 04:295:20:41:59
Block: 79434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106163 RingCT/type: yes/0
Extra: 0178f80bfdd17458ab847ba20c5ff2f5fbe6e7e4f0e44eeef8bab185ce4bf24e11021100000002640ff48f000000000000000000

1 output(s) for total of 334.813510262000 dcy

stealth address amount amount idx
00: 85ec4e211daf1cafbcec6a50ed5e9b85150df45a7b197cd74631bf006bd2478f 334.813510262000 145278 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": 79444, "vin": [ { "gen": { "height": 79434 } } ], "vout": [ { "amount": 334813510262, "target": { "key": "85ec4e211daf1cafbcec6a50ed5e9b85150df45a7b197cd74631bf006bd2478f" } } ], "extra": [ 1, 120, 248, 11, 253, 209, 116, 88, 171, 132, 123, 162, 12, 95, 242, 245, 251, 230, 231, 228, 240, 228, 78, 238, 248, 186, 177, 133, 206, 75, 242, 78, 17, 2, 17, 0, 0, 0, 2, 100, 15, 244, 143, 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