Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd4abca337cf981de8a816ae174a59e301ec0bf5fd2ec26179dca9d6127acef2

Tx prefix hash: e9ddaf0fd855911adaae03c834345e6608a6eb1e919b35e54a51c7c8f46368c7
Tx public key: bc0aae56f137f9bd3caa720e3041a0d6defb2f8de004b5712c39ee7fb758e69b
Timestamp: 1731735912 Timestamp [UTC]: 2024-11-16 05:45:12 Age [y:d:h:m:s]: 01:364:19:37:09
Block: 1154764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524536 RingCT/type: yes/0
Extra: 01bc0aae56f137f9bd3caa720e3041a0d6defb2f8de004b5712c39ee7fb758e69b02110000000a007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a6e83ff4c1e52cece7f6720ff22bc5a43ca881b1f98876d54ec6d26841e2ebe9 0.000600000000 1640377 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": 1154774, "vin": [ { "gen": { "height": 1154764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6e83ff4c1e52cece7f6720ff22bc5a43ca881b1f98876d54ec6d26841e2ebe9" } } ], "extra": [ 1, 188, 10, 174, 86, 241, 55, 249, 189, 60, 170, 114, 14, 48, 65, 160, 214, 222, 251, 47, 141, 224, 4, 181, 113, 44, 57, 238, 127, 183, 88, 230, 155, 2, 17, 0, 0, 0, 10, 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) | monero version: