Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56865187621b88ad16c07f96691b20ac9021b87347f59876569d9c27aac7597d

Tx prefix hash: b497019cf317d5fa35a948a282a0bdc70cae0692ffb38ce25e6a241673fd7f4e
Tx public key: f7bd48275a4e41c70d821ffb2742da48fed2c0b5f7e8bc5ebdf880f20a43edd6
Timestamp: 1704205209 Timestamp [UCT]: 2024-01-02 14:20:09 Age [y:d:h:m:s]: 01:098:19:39:05
Block: 926596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331744 RingCT/type: yes/0
Extra: 01f7bd48275a4e41c70d821ffb2742da48fed2c0b5f7e8bc5ebdf880f20a43edd602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dd29b2e9d02606a377f1c2ee14ecc94296dfce9b9366bf1a0961253048ddc5b 0.600000000000 1384390 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": 926606, "vin": [ { "gen": { "height": 926596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dd29b2e9d02606a377f1c2ee14ecc94296dfce9b9366bf1a0961253048ddc5b" } } ], "extra": [ 1, 247, 189, 72, 39, 90, 78, 65, 199, 13, 130, 31, 251, 39, 66, 218, 72, 254, 210, 192, 181, 247, 232, 188, 94, 189, 248, 128, 242, 10, 67, 237, 214, 2, 17, 0, 0, 0, 6, 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