Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aebbc9560f1f7446eb604e9c504751ad8749bcd4142ed0c43e5d905b268f092

Tx prefix hash: 88d249f87710e6c5339c5b716c6013e6b97099e98af354c5e6643c5acc9b248d
Tx public key: 2e2bf206b6ff591afbee59bb45d547d2fd4bf21b792694ea9d38bcb1d160928f
Timestamp: 1729314185 Timestamp [UCT]: 2024-10-19 05:03:05 Age [y:d:h:m:s]: 00:003:16:33:43
Block: 1134767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2615 RingCT/type: yes/0
Extra: 012e2bf206b6ff591afbee59bb45d547d2fd4bf21b792694ea9d38bcb1d160928f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4a02de7512d1bb34b500597831af9722b429bdf946499ac9968d0204d8917d1 0.600000000000 1618094 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": 1134777, "vin": [ { "gen": { "height": 1134767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4a02de7512d1bb34b500597831af9722b429bdf946499ac9968d0204d8917d1" } } ], "extra": [ 1, 46, 43, 242, 6, 182, 255, 89, 26, 251, 238, 89, 187, 69, 213, 71, 210, 253, 75, 242, 27, 121, 38, 148, 234, 157, 56, 188, 177, 209, 96, 146, 143, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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