Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4e0c7d55e9a4fbddc0ca8dcfa3eafc7814024ba011b30d5a60e814f5f0431df

Tx prefix hash: 7b7be20bc5921422b3ae6bcb7dffa77ff4ce67d8ec69febfdc98870fc3f03183
Tx public key: 004208d8c9b725f8d5657967773152f4c89aab60ae9135b5b7572ab667a0dead
Timestamp: 1741887670 Timestamp [UCT]: 2025-03-13 17:41:10 Age [y:d:h:m:s]: 00:056:14:40:50
Block: 1238557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40477 RingCT/type: yes/0
Extra: 01004208d8c9b725f8d5657967773152f4c89aab60ae9135b5b7572ab667a0dead02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a7e82280e06562e71715df8bf887e8d4469e7d0111867ee285e8a7a9e2558d0 0.600000000000 1725516 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": 1238567, "vin": [ { "gen": { "height": 1238557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a7e82280e06562e71715df8bf887e8d4469e7d0111867ee285e8a7a9e2558d0" } } ], "extra": [ 1, 0, 66, 8, 216, 201, 183, 37, 248, 213, 101, 121, 103, 119, 49, 82, 244, 200, 154, 171, 96, 174, 145, 53, 181, 183, 87, 42, 182, 103, 160, 222, 173, 2, 17, 0, 0, 0, 11, 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