Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91dbca9151cbae9be3bb9f00e541399c890490835d11ea980c4b6c3edfbd502f

Tx prefix hash: 3fa2c9fb3217e06b4937f647d2c9c1ce761576797e429d19b2061be4d2037f0a
Tx public key: 80f3d8a4f629b4fcbb122d65f870b740be96ae151bf6b52a46e8b58a2d79b860
Timestamp: 1705644329 Timestamp [UCT]: 2024-01-19 06:05:29 Age [y:d:h:m:s]: 01:109:00:26:12
Block: 938518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339029 RingCT/type: yes/0
Extra: 0180f3d8a4f629b4fcbb122d65f870b740be96ae151bf6b52a46e8b58a2d79b86002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33df167ba43a6d10f7d12366a5dd63a515bb011f519eecc282cca90a47757805 0.600000000000 1396588 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": 938528, "vin": [ { "gen": { "height": 938518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33df167ba43a6d10f7d12366a5dd63a515bb011f519eecc282cca90a47757805" } } ], "extra": [ 1, 128, 243, 216, 164, 246, 41, 180, 252, 187, 18, 45, 101, 248, 112, 183, 64, 190, 150, 174, 21, 27, 246, 181, 42, 70, 232, 181, 138, 45, 121, 184, 96, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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