Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d861276a01d8f5d60a67b2d5c8e5c70a73b1ae6a8c07629dc5f6e9e32a1b3ba0

Tx prefix hash: adae2c2b8b6120a4dee09e8a2a466e4fb513391ec13c17223fa7e3fe4b004989
Tx public key: 38a7ef5fe09575f3c987dce1031cdbed38fa0a732179f370dc687c3bd86d7a5e
Timestamp: 1704998604 Timestamp [UCT]: 2024-01-11 18:43:24 Age [y:d:h:m:s]: 01:164:04:20:22
Block: 933170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378251 RingCT/type: yes/0
Extra: 0138a7ef5fe09575f3c987dce1031cdbed38fa0a732179f370dc687c3bd86d7a5e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc176282e86c5866c1bf90441c74c1cb04e427bd6db2d8820023083d9ec1541b 0.600000000000 1391128 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": 933180, "vin": [ { "gen": { "height": 933170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc176282e86c5866c1bf90441c74c1cb04e427bd6db2d8820023083d9ec1541b" } } ], "extra": [ 1, 56, 167, 239, 95, 224, 149, 117, 243, 201, 135, 220, 225, 3, 28, 219, 237, 56, 250, 10, 115, 33, 121, 243, 112, 220, 104, 124, 59, 216, 109, 122, 94, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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