Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be4d398fd62c4f7e2a7d8fb4ffd72fc2668b57ed5452c2c9ee6a0b713672154

Tx prefix hash: dcabce8245628dc4a918a89b492579804bc0de36c51b5ada3a329f688eb01f24
Tx public key: 54422f67df66948153b62bd1bfeeac72902d5ace7c9face2a5a54cafba422d7b
Timestamp: 1693819612 Timestamp [UTC]: 2023-09-04 09:26:52 Age [y:d:h:m:s]: 03:079:19:23:47
Block: 840684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 842810 RingCT/type: yes/0
Extra: 0154422f67df66948153b62bd1bfeeac72902d5ace7c9face2a5a54cafba422d7b02110000000b4b8f5122000000000000000000

1 output(s) for total of 0.001005691996 xmr

stealth address amount amount idx tag
00: dab8d076d99628bd5f8bba841f92a1f81f376fcb816f07e325ab096258281164 0.001005691996 1293644 of 0 -

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": 840694, "vin": [ { "gen": { "height": 840684 } } ], "vout": [ { "amount": 1005691996, "target": { "key": "dab8d076d99628bd5f8bba841f92a1f81f376fcb816f07e325ab096258281164" } } ], "extra": [ 1, 84, 66, 47, 103, 223, 102, 148, 129, 83, 182, 43, 209, 191, 238, 172, 114, 144, 45, 90, 206, 124, 159, 172, 226, 165, 165, 76, 175, 186, 66, 45, 123, 2, 17, 0, 0, 0, 11, 75, 143, 81, 34, 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) | monero version: