Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70059c509cae512b7e57117cf3beafaac24e84ea21e43d58341f58035c9a20f4

Tx prefix hash: 0d94578ffbe2441b3380125102efc2202b9f2e8b8599538e7a41311dcb68d47f
Tx public key: 4cb2cc1b75eaaa3df0135c361c887c83e17700075a4f4865a7ecc89a90ae86c1
Timestamp: 1698647113 Timestamp [UCT]: 2023-10-30 06:25:13 Age [y:d:h:m:s]: 01:122:13:40:29
Block: 880739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348573 RingCT/type: yes/0
Extra: 014cb2cc1b75eaaa3df0135c361c887c83e17700075a4f4865a7ecc89a90ae86c1021100000003faf35c9c000000000000000000

1 output(s) for total of 0.740876966000 dcy

stealth address amount amount idx
00: da527c4c5ef124ebde447986cc9f3d40ffeb28203371392d200165d70a00805c 0.740876966000 1336305 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": 880749, "vin": [ { "gen": { "height": 880739 } } ], "vout": [ { "amount": 740876966, "target": { "key": "da527c4c5ef124ebde447986cc9f3d40ffeb28203371392d200165d70a00805c" } } ], "extra": [ 1, 76, 178, 204, 27, 117, 234, 170, 61, 240, 19, 92, 54, 28, 136, 124, 131, 225, 119, 0, 7, 90, 79, 72, 101, 167, 236, 200, 154, 144, 174, 134, 193, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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