Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0673be6b197e9b7405b7853fdf3f0943e69b1d90857c1770709b500007e86a81

Tx prefix hash: ab632c2f60e5f3d9908778336a61684aa1b53fa0fbf85043c724934dd7eb9415
Tx public key: 8d65dae11e9d697a8c7e52c1aa313f9cfc042663e3bb8e5447abfea85823b5a0
Timestamp: 1716899233 Timestamp [UCT]: 2024-05-28 12:27:13 Age [y:d:h:m:s]: 00:156:01:06:20
Block: 1031859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111696 RingCT/type: yes/0
Extra: 018d65dae11e9d697a8c7e52c1aa313f9cfc042663e3bb8e5447abfea85823b5a002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fe7b42da4a90c401320834e324945a5f04ce22d92cd66a96775dcc3b0c82801 0.600000000000 1500308 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": 1031869, "vin": [ { "gen": { "height": 1031859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fe7b42da4a90c401320834e324945a5f04ce22d92cd66a96775dcc3b0c82801" } } ], "extra": [ 1, 141, 101, 218, 225, 30, 157, 105, 122, 140, 126, 82, 193, 170, 49, 63, 156, 252, 4, 38, 99, 227, 187, 142, 84, 71, 171, 254, 168, 88, 35, 181, 160, 2, 17, 0, 0, 0, 3, 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