Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d5804fe447f9dbb14c71cb93acfc777ba67ba820c577efc8092d509184ba0a

Tx prefix hash: 876cad129a500b09c840ab81882a073b4b0f75a74486e182864601f15369dc4a
Tx public key: 04d9b3ab864ca488eba1cf436a0c98feabc5142ec0817bac8b2e3ba7b821e684
Timestamp: 1771987963 Timestamp [UTC]: 2026-02-25 02:52:43 Age [y:d:h:m:s]: 00:268:04:02:50
Block: 1485226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197261 RingCT/type: yes/0
Extra: 0104d9b3ab864ca488eba1cf436a0c98feabc5142ec0817bac8b2e3ba7b821e684021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 04784c6a48b141acc2e763857a3dc812f48366bb2f2eaa6ddc77e60ada7ffee4 0.000600000000 1974660 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": 1485236, "vin": [ { "gen": { "height": 1485226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04784c6a48b141acc2e763857a3dc812f48366bb2f2eaa6ddc77e60ada7ffee4" } } ], "extra": [ 1, 4, 217, 179, 171, 134, 76, 164, 136, 235, 161, 207, 67, 106, 12, 152, 254, 171, 197, 20, 46, 192, 129, 123, 172, 139, 46, 59, 167, 184, 33, 230, 132, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: