Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 733aa1acc902d072fc371b661629f1aaa84b0d7fde2fa87043c2e3d87750b299

Tx prefix hash: 12d48418bbae22d9897e47d204dc7bb4c894c860e307fa43fec205f5c083a0c8
Tx public key: 54e96101cb8f8e6aaee93120f53ca1331825a12d4a8e79bb163037dc3d3d950f
Timestamp: 1716220069 Timestamp [UCT]: 2024-05-20 15:47:49 Age [y:d:h:m:s]: 00:362:17:01:57
Block: 1026225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259267 RingCT/type: yes/0
Extra: 0154e96101cb8f8e6aaee93120f53ca1331825a12d4a8e79bb163037dc3d3d950f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c15f4ee301e40317690a42083e29de14c2be990009ec0f746de16d5c30f81685 0.600000000000 1493190 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": 1026235, "vin": [ { "gen": { "height": 1026225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c15f4ee301e40317690a42083e29de14c2be990009ec0f746de16d5c30f81685" } } ], "extra": [ 1, 84, 233, 97, 1, 203, 143, 142, 106, 174, 233, 49, 32, 245, 60, 161, 51, 24, 37, 161, 45, 74, 142, 121, 187, 22, 48, 55, 220, 61, 61, 149, 15, 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