Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 418c76a3b5f76712a90a144ff3392658c3fe2ad08c4d4dc983796a2c4c520604

Tx prefix hash: a6b53af195a541ad665eacca580a3a470505b41f2fa9b89f971b1cd5815f327e
Tx public key: 2192fcc31d7ddff80ccb881bbd38e55c8d2d258c681cf93546806c8dd83e7606
Timestamp: 1711182962 Timestamp [UCT]: 2024-03-23 08:36:02 Age [y:d:h:m:s]: 01:087:02:09:57
Block: 984479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323124 RingCT/type: yes/0
Extra: 012192fcc31d7ddff80ccb881bbd38e55c8d2d258c681cf93546806c8dd83e760602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b19bb10efeba2a446250f32fddbb6f2b3052a2ca6fbf4bc57b2624cc2d983a7 0.600000000000 1444650 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": 984489, "vin": [ { "gen": { "height": 984479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b19bb10efeba2a446250f32fddbb6f2b3052a2ca6fbf4bc57b2624cc2d983a7" } } ], "extra": [ 1, 33, 146, 252, 195, 29, 125, 223, 248, 12, 203, 136, 27, 189, 56, 229, 92, 141, 45, 37, 140, 104, 28, 249, 53, 70, 128, 108, 141, 216, 62, 118, 6, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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