Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acadf33ac66d75e0622cb1429d05beb3d9e7a5365c869973c7c91c9826334839

Tx prefix hash: 8e513fed16b1a8eddeaf3becf8c2b509e08fa0fd0e1335765a60216b190c8753
Tx public key: 0004b3143cde7a8c905e62217de8412221111471cc055d48c721fc7c8b44c74c
Timestamp: 1632697582 Timestamp [UCT]: 2021-09-26 23:06:22 Age [y:d:h:m:s]: 03:004:05:16:52
Block: 341513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 779636 RingCT/type: yes/0
Extra: 010004b3143cde7a8c905e62217de8412221111471cc055d48c721fc7c8b44c74c0211000000198d0de867000000000000000000

1 output(s) for total of 45.334214453000 dcy

stealth address amount amount idx
00: fed8d23430aad3b9fab155845e5516ab3ec84f084fab11fb730f97b555bf958f 45.334214453000 701619 of 0

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": 341523, "vin": [ { "gen": { "height": 341513 } } ], "vout": [ { "amount": 45334214453, "target": { "key": "fed8d23430aad3b9fab155845e5516ab3ec84f084fab11fb730f97b555bf958f" } } ], "extra": [ 1, 0, 4, 179, 20, 60, 222, 122, 140, 144, 94, 98, 33, 125, 232, 65, 34, 33, 17, 20, 113, 204, 5, 93, 72, 199, 33, 252, 124, 139, 68, 199, 76, 2, 17, 0, 0, 0, 25, 141, 13, 232, 103, 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