Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6de48abfd777550d4d5d31f4c51dcce2e91e4e93efe974837fdf5c3f052d52d3

Tx prefix hash: b4af92c98b791d5d816260f30735e300006aff3ec05fcecf5e49bf643340a073
Tx public key: 8f9597de09ffd9963b1894ae48510d51833bac15c802ec12bcdb400b2c0f792d
Timestamp: 1720598661 Timestamp [UCT]: 2024-07-10 08:04:21 Age [y:d:h:m:s]: 01:164:00:44:15
Block: 1062528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375799 RingCT/type: yes/0
Extra: 018f9597de09ffd9963b1894ae48510d51833bac15c802ec12bcdb400b2c0f792d02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d6eabd7d1b0b4e3dedd418dcb719442f08549a004db5edc9748a1bc30d19f9e 0.600000000000 1533033 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": 1062538, "vin": [ { "gen": { "height": 1062528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d6eabd7d1b0b4e3dedd418dcb719442f08549a004db5edc9748a1bc30d19f9e" } } ], "extra": [ 1, 143, 149, 151, 222, 9, 255, 217, 150, 59, 24, 148, 174, 72, 81, 13, 81, 131, 59, 172, 21, 200, 2, 236, 18, 188, 219, 64, 11, 44, 15, 121, 45, 2, 17, 0, 0, 0, 7, 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