Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2679702d13267ae4db44447c3f0c5bc8d6b3113b00a4b96e4fb28e11673ea5f3

Tx prefix hash: 9f3fcb72e4e007a0c2c0f5ba2f6a82c7b6e8ac022c21835e9332047f1ac6a8ef
Tx public key: 9fea1efbfe09e741e8be4175f8c40ae34cf015e527dac62e7cf9c430856a6a0d
Timestamp: 1739748946 Timestamp [UCT]: 2025-02-16 23:35:46 Age [y:d:h:m:s]: 00:312:17:13:59
Block: 1220805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221338 RingCT/type: yes/0
Extra: 019fea1efbfe09e741e8be4175f8c40ae34cf015e527dac62e7cf9c430856a6a0d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 543bc14d4d3f776857646ab1f61f9e11297e851cf1f16d0722a327570b54ad37 0.600000000000 1707646 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": 1220815, "vin": [ { "gen": { "height": 1220805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "543bc14d4d3f776857646ab1f61f9e11297e851cf1f16d0722a327570b54ad37" } } ], "extra": [ 1, 159, 234, 30, 251, 254, 9, 231, 65, 232, 190, 65, 117, 248, 196, 10, 227, 76, 240, 21, 229, 39, 218, 198, 46, 124, 249, 196, 48, 133, 106, 106, 13, 2, 17, 0, 0, 0, 1, 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