Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2fbf0b9d6e50b9a700f40181bf013333ff892ef9f6c0118fb647261afd4de39

Tx prefix hash: 469eb70a0647b1fe22e07199fed402026a77a9c26b8b827c7e7cd78c50302d6d
Tx public key: 582183c68fe0ef8aff29f5cdc72921b37a0ed566d541dafa10c779e0dbe4541d
Timestamp: 1738532719 Timestamp [UCT]: 2025-02-02 21:45:19 Age [y:d:h:m:s]: 00:247:10:04:43
Block: 1210763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174542 RingCT/type: yes/0
Extra: 01582183c68fe0ef8aff29f5cdc72921b37a0ed566d541dafa10c779e0dbe4541d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d44f6f5a3185f5b03085b371094e971ef037b1e9229819f591fee76553afbacd 0.600000000000 1697518 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": 1210773, "vin": [ { "gen": { "height": 1210763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d44f6f5a3185f5b03085b371094e971ef037b1e9229819f591fee76553afbacd" } } ], "extra": [ 1, 88, 33, 131, 198, 143, 224, 239, 138, 255, 41, 245, 205, 199, 41, 33, 179, 122, 14, 213, 102, 213, 65, 218, 250, 16, 199, 121, 224, 219, 228, 84, 29, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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