Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d56fc2dc21910f14fe8e8760f3848fed9a745c7e155cffd4a029ba4d42492ecc

Tx prefix hash: e1aed899fdd4d70bf1629616a19e31fe0c1e0c5f690949fdac86b206118a00f4
Tx public key: e4d56b5bdad7a7648e5acfeeef013d1d95ce244650b4b2666163387a2db5fef6
Timestamp: 1718021738 Timestamp [UCT]: 2024-06-10 12:15:38 Age [y:d:h:m:s]: 00:138:05:19:19
Block: 1041161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98975 RingCT/type: yes/0
Extra: 01e4d56b5bdad7a7648e5acfeeef013d1d95ce244650b4b2666163387a2db5fef6021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0cd48e316c80fcda08e134cb95f7240452c614c477e81efeb35b436f81875cd 0.600000000000 1509826 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": 1041171, "vin": [ { "gen": { "height": 1041161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0cd48e316c80fcda08e134cb95f7240452c614c477e81efeb35b436f81875cd" } } ], "extra": [ 1, 228, 213, 107, 91, 218, 215, 167, 100, 142, 90, 207, 238, 239, 1, 61, 29, 149, 206, 36, 70, 80, 180, 178, 102, 97, 99, 56, 122, 45, 181, 254, 246, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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