Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56cd7297aad081fc106202a048799781f7a44eebde6b485d0e47daa1ea0e4d0e

Tx prefix hash: a59953e943abbcfc4e0f8d15e4a1a2b9f69859cb10b172536cbaa6fbf1cacdb1
Tx public key: 809f28f8e37eea63a6dcdb6fe7190b03741befff9a3fba8cc8cd08932e95af3b
Timestamp: 1761760636 Timestamp [UCT]: 2025-10-29 17:57:16 Age [y:d:h:m:s]: 00:068:03:10:30
Block: 1400658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48792 RingCT/type: yes/0
Extra: 01809f28f8e37eea63a6dcdb6fe7190b03741befff9a3fba8cc8cd08932e95af3b02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab3abdc983c476c6c789618e9ece183b7831ef5c0cc663e7aa5295bc421d3915 0.600000000000 1888975 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": 1400668, "vin": [ { "gen": { "height": 1400658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab3abdc983c476c6c789618e9ece183b7831ef5c0cc663e7aa5295bc421d3915" } } ], "extra": [ 1, 128, 159, 40, 248, 227, 126, 234, 99, 166, 220, 219, 111, 231, 25, 11, 3, 116, 27, 239, 255, 154, 63, 186, 140, 200, 205, 8, 147, 46, 149, 175, 59, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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