Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88833b8dd261b5f195788f757173d7ca05f0dafbee8ee21a9ef272a85f490d9d

Tx prefix hash: 24a3df58ea8ef0a440d71177344a951586943063c58e85faede0e1c9b961e191
Tx public key: bbfba866eb4345d89801382d585b6b606f8ae86870fdb3fb04a385fd16b56c9b
Timestamp: 1704993625 Timestamp [UCT]: 2024-01-11 17:20:25 Age [y:d:h:m:s]: 01:125:11:10:09
Block: 933134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350787 RingCT/type: yes/0
Extra: 01bbfba866eb4345d89801382d585b6b606f8ae86870fdb3fb04a385fd16b56c9b02110000001159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f636dc4a37c377f9348e9dee725c0e7ffca85ef2336f3545e678d0e2596b465b 0.600000000000 1391090 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": 933144, "vin": [ { "gen": { "height": 933134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f636dc4a37c377f9348e9dee725c0e7ffca85ef2336f3545e678d0e2596b465b" } } ], "extra": [ 1, 187, 251, 168, 102, 235, 67, 69, 216, 152, 1, 56, 45, 88, 91, 107, 96, 111, 138, 232, 104, 112, 253, 179, 251, 4, 163, 133, 253, 22, 181, 108, 155, 2, 17, 0, 0, 0, 17, 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