Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 443aa53fcc391246dd9cb2d1aeca7cf2f0d3d590b0528349680563fd050f40d9

Tx prefix hash: aae07df2ce408a7e263a3ffbdf6dc3c120eb11df76d93773f3177f775c49ac6e
Tx public key: c0087258a151504ad8067c747053ce274817f6a8c238785d55a524968efdb96f
Timestamp: 1687815825 Timestamp [UCT]: 2023-06-26 21:43:45 Age [y:d:h:m:s]: 01:206:05:54:22
Block: 790997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408762 RingCT/type: yes/0
Extra: 01c0087258a151504ad8067c747053ce274817f6a8c238785d55a524968efdb96f0211000000034b8f5122000000000000000000

1 output(s) for total of 1.469260231000 dcy

stealth address amount amount idx
00: f4a0ed4d6d8ab7cfb27323dbd23793e18c155892601456d6faeb0e5348e4ca5f 1.469260231000 1241452 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": 791007, "vin": [ { "gen": { "height": 790997 } } ], "vout": [ { "amount": 1469260231, "target": { "key": "f4a0ed4d6d8ab7cfb27323dbd23793e18c155892601456d6faeb0e5348e4ca5f" } } ], "extra": [ 1, 192, 8, 114, 88, 161, 81, 80, 74, 216, 6, 124, 116, 112, 83, 206, 39, 72, 23, 246, 168, 194, 56, 120, 93, 85, 165, 36, 150, 142, 253, 185, 111, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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