Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27b814c46577d8342ff2ca16258fcf920784f12b7055f3ef233ceb3435e5c643

Tx prefix hash: 918a67e8cac1e40d72e09ff0221d0f67fb230c4f88fa744cd04ad6b45a87ebe8
Tx public key: b156bd554c7e32ae72b147965e44b6a3ec820de5b4b8783c4e8cf8f52a69056c
Timestamp: 1709718932 Timestamp [UCT]: 2024-03-06 09:55:32 Age [y:d:h:m:s]: 01:086:17:27:05
Block: 972334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323014 RingCT/type: yes/0
Extra: 01b156bd554c7e32ae72b147965e44b6a3ec820de5b4b8783c4e8cf8f52a69056c0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9164fc4a3e7f07ff67da3f6dff1158cdb06f17a5dc39401c618555c285c7408 0.600000000000 1432245 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": 972344, "vin": [ { "gen": { "height": 972334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9164fc4a3e7f07ff67da3f6dff1158cdb06f17a5dc39401c618555c285c7408" } } ], "extra": [ 1, 177, 86, 189, 85, 76, 126, 50, 174, 114, 177, 71, 150, 94, 68, 182, 163, 236, 130, 13, 229, 180, 184, 120, 60, 78, 140, 248, 245, 42, 105, 5, 108, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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