Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d5be7b3fd428f33be33eed38280670211692dbf78c5f8ccd20961cc245a28e0

Tx prefix hash: b788ee06c3622503da41acbf34a1d8102d2dd37c96c2a5dbd9c09710d9728079
Tx public key: 35a6a6718208f48c2fdf3447a8bda5c31cedf5b02af3d42d696e61c861ec4808
Timestamp: 1726091547 Timestamp [UCT]: 2024-09-11 21:52:27 Age [y:d:h:m:s]: 00:208:22:23:14
Block: 1108053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149153 RingCT/type: yes/0
Extra: 0135a6a6718208f48c2fdf3447a8bda5c31cedf5b02af3d42d696e61c861ec4808021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57436f7982a2bc3b06397d61c0d0e73eb2ff9f1e8f48ca4739d5d8ebc842df39 0.600000000000 1585814 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": 1108063, "vin": [ { "gen": { "height": 1108053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57436f7982a2bc3b06397d61c0d0e73eb2ff9f1e8f48ca4739d5d8ebc842df39" } } ], "extra": [ 1, 53, 166, 166, 113, 130, 8, 244, 140, 47, 223, 52, 71, 168, 189, 165, 195, 28, 237, 245, 176, 42, 243, 212, 45, 105, 110, 97, 200, 97, 236, 72, 8, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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