Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16e6786f4d8bc62681da957a493ad1569b1157e6e6039679044c0097fc45936f

Tx prefix hash: 4844c7bae3afb80da91d2c0acad16458f2ab5725fb18964fb85bbd08c00fdc1e
Tx public key: c5784c9cbd2c64d503fa68feebc90efbc83c32e232ef53182045b9c576e92d30
Timestamp: 1723118163 Timestamp [UCT]: 2024-08-08 11:56:03 Age [y:d:h:m:s]: 00:107:20:19:36
Block: 1083399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77160 RingCT/type: yes/0
Extra: 01c5784c9cbd2c64d503fa68feebc90efbc83c32e232ef53182045b9c576e92d3002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38692b4b154a4e6a0758f2e8b58253271eb4caf2e594f15e2e378f80aa0c37b4 0.600000000000 1557306 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": 1083409, "vin": [ { "gen": { "height": 1083399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38692b4b154a4e6a0758f2e8b58253271eb4caf2e594f15e2e378f80aa0c37b4" } } ], "extra": [ 1, 197, 120, 76, 156, 189, 44, 100, 213, 3, 250, 104, 254, 235, 201, 14, 251, 200, 60, 50, 226, 50, 239, 83, 24, 32, 69, 185, 197, 118, 233, 45, 48, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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