Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beded41fb8a4052c14edbea913ae90a3f12cddbd42d9feac58db05e485a82508

Tx prefix hash: d5af1ad5845d93cb234c3e65fd448ef063e39c095474200fb766acbf3589a943
Tx public key: 58dda058cc7e4f7c60a20bbda8969d6ac1943c2299d86f80f4f4f1bef37bacd0
Timestamp: 1713914018 Timestamp [UCT]: 2024-04-23 23:13:38 Age [y:d:h:m:s]: 01:190:01:38:28
Block: 1007106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394483 RingCT/type: yes/0
Extra: 0158dda058cc7e4f7c60a20bbda8969d6ac1943c2299d86f80f4f4f1bef37bacd00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08554279bd698f29c4cb81ae0fe51f394e0e3834f22e20e0893e4f1ce352116f 0.600000000000 1468340 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": 1007116, "vin": [ { "gen": { "height": 1007106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08554279bd698f29c4cb81ae0fe51f394e0e3834f22e20e0893e4f1ce352116f" } } ], "extra": [ 1, 88, 221, 160, 88, 204, 126, 79, 124, 96, 162, 11, 189, 168, 150, 157, 106, 193, 148, 60, 34, 153, 216, 111, 128, 244, 244, 241, 190, 243, 123, 172, 208, 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