Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 487ef9942c3a05aa8dd2ddef9a0824b969ce1c60fed5e7578d45898ddbed0c5c

Tx prefix hash: 057b3832a40a1ae9d7768bcc11598c03c5766e29f4824e37c6454df5c055aaa0
Tx public key: b332d7d2eeab53589a61f5aa747bf5c1d5afae9471f38d7cf3513f715b305012
Timestamp: 1727815529 Timestamp [UCT]: 2024-10-01 20:45:29 Age [y:d:h:m:s]: 00:187:14:34:07
Block: 1122355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133874 RingCT/type: yes/0
Extra: 01b332d7d2eeab53589a61f5aa747bf5c1d5afae9471f38d7cf3513f715b30501202110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: feda9be0d26ce6bcd8e44748b0a66b3c8dfb41106ffe7885fcd9ee40d31bb90e 0.600000000000 1604778 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": 1122365, "vin": [ { "gen": { "height": 1122355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "feda9be0d26ce6bcd8e44748b0a66b3c8dfb41106ffe7885fcd9ee40d31bb90e" } } ], "extra": [ 1, 179, 50, 215, 210, 238, 171, 83, 88, 154, 97, 245, 170, 116, 123, 245, 193, 213, 175, 174, 148, 113, 243, 141, 124, 243, 81, 63, 113, 91, 48, 80, 18, 2, 17, 0, 0, 0, 3, 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