Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4262825ec796f4292e6c8aeb400e78681ca8e1420e5a666602c2e6b3dd19a328

Tx prefix hash: 746ebf1465fa95ee0aba20ec77d1c62e428727de191961f3f0c1a88ac0da3277
Tx public key: aed5a654d7fe1ce5ecd3e59b3a0499222c87abd2c0c9af150cf515bde84fadb6
Timestamp: 1747064283 Timestamp [UTC]: 2025-05-12 15:38:03 Age [y:d:h:m:s]: 01:187:02:29:04
Block: 1281394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397674 RingCT/type: yes/0
Extra: 01aed5a654d7fe1ce5ecd3e59b3a0499222c87abd2c0c9af150cf515bde84fadb602110000000c1f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d1ae8297b580ef2b87a3fe80f7313fd862cfef87cf05317f38f925affe924030 0.000600000000 1768793 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": 1281404, "vin": [ { "gen": { "height": 1281394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1ae8297b580ef2b87a3fe80f7313fd862cfef87cf05317f38f925affe924030" } } ], "extra": [ 1, 174, 213, 166, 84, 215, 254, 28, 229, 236, 211, 229, 155, 58, 4, 153, 34, 44, 135, 171, 210, 192, 201, 175, 21, 12, 245, 21, 189, 232, 79, 173, 182, 2, 17, 0, 0, 0, 12, 31, 144, 81, 122, 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: