Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03655e3d2bf21dd9724545dc3f65ab4a2cff85551704933ebd5d6c3285ae37c2

Tx prefix hash: 69f554e3caec232cc6c8e95236321bc5674a6023879eae42efc1755b026083ea
Tx public key: b0e6e7e64535bac532de5a7bb52455bf61801d7c2065d3c219692c195868811f
Timestamp: 1737800669 Timestamp [UCT]: 2025-01-25 10:24:29 Age [y:d:h:m:s]: 00:143:08:08:15
Block: 1204936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102181 RingCT/type: yes/0
Extra: 01b0e6e7e64535bac532de5a7bb52455bf61801d7c2065d3c219692c195868811f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a427fae82911a85318ea5a8bd100b12c6f3dc3fa582e6c5058877a9969ec0ca 0.600000000000 1691631 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": 1204946, "vin": [ { "gen": { "height": 1204936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a427fae82911a85318ea5a8bd100b12c6f3dc3fa582e6c5058877a9969ec0ca" } } ], "extra": [ 1, 176, 230, 231, 230, 69, 53, 186, 197, 50, 222, 90, 123, 181, 36, 85, 191, 97, 128, 29, 124, 32, 101, 211, 194, 25, 105, 44, 25, 88, 104, 129, 31, 2, 17, 0, 0, 0, 4, 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