Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 481016459f5274453a75c6791e14f9ee76d0075d7c9e46a21125cf391ee7cae1

Tx prefix hash: 3f22a9066b333dc4c8c81fc5b32e2126eeead70c52ef94472cf14333863604e1
Tx public key: 54ea69d089bff1b822a6e83e88376f32c755f1656d186ec89251be1b69666c25
Timestamp: 1714597346 Timestamp [UCT]: 2024-05-01 21:02:26 Age [y:d:h:m:s]: 00:338:00:42:21
Block: 1012768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241624 RingCT/type: yes/0
Extra: 0154ea69d089bff1b822a6e83e88376f32c755f1656d186ec89251be1b69666c250211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4dfc52ab874b5d32adfb48ff46ac3d3b76c79b1a20e122496cdd7a456d13a82 0.600000000000 1475392 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": 1012778, "vin": [ { "gen": { "height": 1012768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4dfc52ab874b5d32adfb48ff46ac3d3b76c79b1a20e122496cdd7a456d13a82" } } ], "extra": [ 1, 84, 234, 105, 208, 137, 191, 241, 184, 34, 166, 232, 62, 136, 55, 111, 50, 199, 85, 241, 101, 109, 24, 110, 200, 146, 81, 190, 27, 105, 102, 108, 37, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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