Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d50a7e4498677a3dd8e74cc25209701eec7860d2145333f13a03859fe5adc20

Tx prefix hash: a6c33f783c4d6341dfcd926c27bb534cd519dacf118df52f50d3240d6692536e
Tx public key: 8272e56915d1c1904897ea758a7bf37ef7e4bafd6d7cbd65bbd14fd8fecb1baf
Timestamp: 1705167540 Timestamp [UCT]: 2024-01-13 17:39:00 Age [y:d:h:m:s]: 01:083:09:25:32
Block: 934570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320695 RingCT/type: yes/0
Extra: 018272e56915d1c1904897ea758a7bf37ef7e4bafd6d7cbd65bbd14fd8fecb1baf0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b12ae826134245f21e2474a8495720230bbb5d0c4bc5c9d3f609a66c9f2b0204 0.600000000000 1392584 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": 934580, "vin": [ { "gen": { "height": 934570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b12ae826134245f21e2474a8495720230bbb5d0c4bc5c9d3f609a66c9f2b0204" } } ], "extra": [ 1, 130, 114, 229, 105, 21, 209, 193, 144, 72, 151, 234, 117, 138, 123, 243, 126, 247, 228, 186, 253, 109, 124, 189, 101, 187, 209, 79, 216, 254, 203, 27, 175, 2, 17, 0, 0, 0, 9, 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