Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 335427c85376e8b3350b6b5ecd0656d3b8acede1815e6ee7aad16c280a8dfab8

Tx prefix hash: 290f2c90eaed4b36f4dd312b1ec37e9062cd00eb2f5f72e06e4e26c2f596a1b3
Tx public key: e9c1150f3c03bb14c8625bc739a293c628d2ac6bf7d30dfe185e7136c94a0bcd
Timestamp: 1714787609 Timestamp [UCT]: 2024-05-04 01:53:29 Age [y:d:h:m:s]: 00:335:20:15:37
Block: 1014349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240059 RingCT/type: yes/0
Extra: 01e9c1150f3c03bb14c8625bc739a293c628d2ac6bf7d30dfe185e7136c94a0bcd0211000000013f82f9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c560672fd7d6fedb845fd048675f2aa9788eac9e4cb80f36179d65983a599e9e 0.600000000000 1477414 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": 1014359, "vin": [ { "gen": { "height": 1014349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c560672fd7d6fedb845fd048675f2aa9788eac9e4cb80f36179d65983a599e9e" } } ], "extra": [ 1, 233, 193, 21, 15, 60, 3, 187, 20, 200, 98, 91, 199, 57, 162, 147, 198, 40, 210, 172, 107, 247, 211, 13, 254, 24, 94, 113, 54, 201, 74, 11, 205, 2, 17, 0, 0, 0, 1, 63, 130, 249, 251, 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