Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cdc0d4a5e17bb9e511820949bb70ae61aabec2d3e74da746944f133a01ab0d4

Tx prefix hash: 7ca3528972818abd0e75ca1675c431348d77953a98441be787e922a7807b6963
Tx public key: e36a04a5b1647722e9dcf185d6f453faeac97eb05df50234407f9cb507754b7d
Timestamp: 1713308247 Timestamp [UTC]: 2024-04-16 22:57:27 Age [y:d:h:m:s]: 02:218:16:51:28
Block: 1002062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 681432 RingCT/type: yes/0
Extra: 01e36a04a5b1647722e9dcf185d6f453faeac97eb05df50234407f9cb507754b7d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8d5a7f19279c13b156e2630595d13d8eb5382ee89dd379eca1f065af8729527b 0.000600000000 1462576 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": 1002072, "vin": [ { "gen": { "height": 1002062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d5a7f19279c13b156e2630595d13d8eb5382ee89dd379eca1f065af8729527b" } } ], "extra": [ 1, 227, 106, 4, 165, 177, 100, 119, 34, 233, 220, 241, 133, 214, 244, 83, 250, 234, 201, 126, 176, 93, 245, 2, 52, 64, 127, 156, 181, 7, 117, 75, 125, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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: