Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0233cd98704dc20fa2d0cc6cc0c7b3c0de4a853ccde647af4e165a8ccbcb0f76

Tx prefix hash: 590cfd88732f805302fb2d32316db17ca3d20aeacca1cc2d80b466de5314f59c
Tx public key: afc00272560f678546b7c5ee1e93e504cdd98d6fd08f1b945374214bc64d9b5f
Timestamp: 1737382343 Timestamp [UTC]: 2025-01-20 14:12:23 Age [y:d:h:m:s]: 01:299:08:47:54
Block: 1201464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477756 RingCT/type: yes/0
Extra: 01afc00272560f678546b7c5ee1e93e504cdd98d6fd08f1b945374214bc64d9b5f021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 748bbc2ecf4eb29156af6b786047895e73b9d3f3ead39b2053dd9bc89c7f7b7b 0.000600000000 1688117 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": 1201474, "vin": [ { "gen": { "height": 1201464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "748bbc2ecf4eb29156af6b786047895e73b9d3f3ead39b2053dd9bc89c7f7b7b" } } ], "extra": [ 1, 175, 192, 2, 114, 86, 15, 103, 133, 70, 183, 197, 238, 30, 147, 229, 4, 205, 217, 141, 111, 208, 143, 27, 148, 83, 116, 33, 75, 198, 77, 155, 95, 2, 17, 0, 0, 0, 6, 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: