Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e38b171aec153f0912d652e22b08efd4a606e3f17ec1f5ced99ca3202daf6cf

Tx prefix hash: 56bd96c38038af4e3b9782bfeac7714fe116bdeceba4c2720656fee065181a8c
Tx public key: 44f637a8e1d047bf4f969fe617f50a13021d6d07163b06901f42ff5f1f0c0bc1
Timestamp: 1739855456 Timestamp [UTC]: 2025-02-18 05:10:56 Age [y:d:h:m:s]: 01:011:14:33:48
Block: 1221686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266872 RingCT/type: yes/0
Extra: 0144f637a8e1d047bf4f969fe617f50a13021d6d07163b06901f42ff5f1f0c0bc1021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 80ef68ac70a2f12b28e15d5860a918da0cad137ecd4bc5f053fd40fbadf633a7 0.000600000000 1708533 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 dinastycoin-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": 1221696, "vin": [ { "gen": { "height": 1221686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80ef68ac70a2f12b28e15d5860a918da0cad137ecd4bc5f053fd40fbadf633a7" } } ], "extra": [ 1, 68, 246, 55, 168, 225, 208, 71, 191, 79, 150, 159, 230, 23, 245, 10, 19, 2, 29, 109, 7, 22, 59, 6, 144, 31, 66, 255, 95, 31, 12, 11, 193, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369