Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f05985a637ee0fef59b9e6842e1ea558ac5ce88b4b9575086d7187f3e8c3907f

Tx prefix hash: f3c6f83957f99207822afe1c195271c81bde6575b37820c8e86296993deb900f
Tx public key: 8f4004d7fc7b65c6fb74ae0d22ce65969c5157d157b2e940efe432e2d4be57eb
Timestamp: 1715979067 Timestamp [UCT]: 2024-05-17 20:51:07 Age [y:d:h:m:s]: 00:238:07:49:20
Block: 1024226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170566 RingCT/type: yes/0
Extra: 018f4004d7fc7b65c6fb74ae0d22ce65969c5157d157b2e940efe432e2d4be57eb021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccdce85fc833265557417a757ba5ccc48be318d30bf1d4eb898bff1e145f65cb 0.600000000000 1489801 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": 1024236, "vin": [ { "gen": { "height": 1024226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccdce85fc833265557417a757ba5ccc48be318d30bf1d4eb898bff1e145f65cb" } } ], "extra": [ 1, 143, 64, 4, 215, 252, 123, 101, 198, 251, 116, 174, 13, 34, 206, 101, 150, 156, 81, 87, 209, 87, 178, 233, 64, 239, 228, 50, 226, 212, 190, 87, 235, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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