Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a214135e4fd3a88e6ccc9a10503a6537d00d714c94be539b7df019c17f95738c

Tx prefix hash: 04eacbcffb0b41c25d3cf04881616608c199d4430beb8cd097f5600f2a025578
Tx public key: 085a7a53463ce69a192425aa272a12f5475dbd987b9fbccd0e704a16135f3c78
Timestamp: 1728916433 Timestamp [UCT]: 2024-10-14 14:33:53 Age [y:d:h:m:s]: 00:222:05:28:18
Block: 1131481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158639 RingCT/type: yes/0
Extra: 01085a7a53463ce69a192425aa272a12f5475dbd987b9fbccd0e704a16135f3c7802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cd06ebdd8f046334ab69c87fba823dfb6e6caa28e75fa86db1e2c544258ea83 0.600000000000 1614384 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": 1131491, "vin": [ { "gen": { "height": 1131481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cd06ebdd8f046334ab69c87fba823dfb6e6caa28e75fa86db1e2c544258ea83" } } ], "extra": [ 1, 8, 90, 122, 83, 70, 60, 230, 154, 25, 36, 37, 170, 39, 42, 18, 245, 71, 93, 189, 152, 123, 159, 188, 205, 14, 112, 74, 22, 19, 95, 60, 120, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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