Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4b78e343bd2f921ea4b7c3e06d70d444ec009674ab07f7a808b2033c05a28f1

Tx prefix hash: 8754e73272447d1b230bb3c3bf2a6c29b289ce18fed1b1cd3599bef76caf654f
Tx public key: 185d942a0c38ab831ed8f4ddce7aa32f56f8a4925847c63aae75997a223580d9
Timestamp: 1764158881 Timestamp [UCT]: 2025-11-26 12:08:01 Age [y:d:h:m:s]: 00:043:02:27:13
Block: 1420523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30874 RingCT/type: yes/0
Extra: 01185d942a0c38ab831ed8f4ddce7aa32f56f8a4925847c63aae75997a223580d9021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a94dd859dbb136cbde921880faccc636bb72c39f5ffbbf758c84e93747746629 0.600000000000 1909068 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": 1420533, "vin": [ { "gen": { "height": 1420523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a94dd859dbb136cbde921880faccc636bb72c39f5ffbbf758c84e93747746629" } } ], "extra": [ 1, 24, 93, 148, 42, 12, 56, 171, 131, 30, 216, 244, 221, 206, 122, 163, 47, 86, 248, 164, 146, 88, 71, 198, 58, 174, 117, 153, 122, 34, 53, 128, 217, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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