Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd7a19f1db98b8cea1dd953fd548f881e226d9def9b375dcda689bf963e8f224

Tx prefix hash: 4236880f4e13562dc57f2d52ceddf764fb4596430a42c4c7c2b40365449b82d9
Tx public key: e20b32342714c0c4d4c9a5ea4815d74a19a8f0641be166fb03595f9e2cd0134c
Timestamp: 1712607880 Timestamp [UCT]: 2024-04-08 20:24:40 Age [y:d:h:m:s]: 01:259:03:08:30
Block: 996240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443943 RingCT/type: yes/0
Extra: 01e20b32342714c0c4d4c9a5ea4815d74a19a8f0641be166fb03595f9e2cd0134c02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f0ad9c52f3798c86de27abc4ff2d1f943c89d28c4399b181ebd0c6179fb5737 0.600000000000 1456656 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": 996250, "vin": [ { "gen": { "height": 996240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f0ad9c52f3798c86de27abc4ff2d1f943c89d28c4399b181ebd0c6179fb5737" } } ], "extra": [ 1, 226, 11, 50, 52, 39, 20, 192, 196, 212, 201, 165, 234, 72, 21, 215, 74, 25, 168, 240, 100, 27, 225, 102, 251, 3, 89, 95, 158, 44, 208, 19, 76, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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