Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b779017bc7d6ee9e57bf0d59c03053979a9c5bc4c754f61fbb7ff26c23ae5b08

Tx prefix hash: 29a023079e19e19a0fd8f777107e96b1a0e101eb3eaba0280550e762d2ac61b2
Tx public key: 0a7410fca06c0470d9b90ec2b9dc6f77a5245e3441ab9ef7b2cff3e91df69c38
Timestamp: 1578925375 Timestamp [UCT]: 2020-01-13 14:22:55 Age [y:d:h:m:s]: 04:318:10:37:04
Block: 44696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117073 RingCT/type: yes/0
Extra: 010a7410fca06c0470d9b90ec2b9dc6f77a5245e3441ab9ef7b2cff3e91df69c380211000000ab2264afe6000000000000000000

1 output(s) for total of 436.419792586000 dcy

stealth address amount amount idx
00: 31a57fc9903cad94d546bbae3507df09fa1da0f77e84b28ac2c888c2b15c4e65 436.419792586000 81415 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": 44706, "vin": [ { "gen": { "height": 44696 } } ], "vout": [ { "amount": 436419792586, "target": { "key": "31a57fc9903cad94d546bbae3507df09fa1da0f77e84b28ac2c888c2b15c4e65" } } ], "extra": [ 1, 10, 116, 16, 252, 160, 108, 4, 112, 217, 185, 14, 194, 185, 220, 111, 119, 165, 36, 94, 52, 65, 171, 158, 247, 178, 207, 243, 233, 29, 246, 156, 56, 2, 17, 0, 0, 0, 171, 34, 100, 175, 230, 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