Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc27a1da42c3c237aa9f17f0e38ca7c7977f5ba9e6c31630dc353090e5efe3f5

Tx prefix hash: 8d51558bbbb1b4484e81599d7cfa2f76a63219d22eae425344d161d76883f9f6
Tx public key: 75dc6c05393ab6c617af24a76b04d4b8811dd465078c425de498be372d6294bf
Timestamp: 1723537089 Timestamp [UCT]: 2024-08-13 08:18:09 Age [y:d:h:m:s]: 00:262:07:29:45
Block: 1086883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187365 RingCT/type: yes/0
Extra: 0175dc6c05393ab6c617af24a76b04d4b8811dd465078c425de498be372d6294bf021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ba6ab613ce5ebf0a3298807387a3b34f221c1be18b7515babfc17fa71692adc 0.600000000000 1561482 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": 1086893, "vin": [ { "gen": { "height": 1086883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ba6ab613ce5ebf0a3298807387a3b34f221c1be18b7515babfc17fa71692adc" } } ], "extra": [ 1, 117, 220, 108, 5, 57, 58, 182, 198, 23, 175, 36, 167, 107, 4, 212, 184, 129, 29, 212, 101, 7, 140, 66, 93, 228, 152, 190, 55, 45, 98, 148, 191, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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