Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e250803e925da4510629f921237ecde7bedcdccc710f0779fbddc0f750aaba6

Tx prefix hash: 9bc1fdb566da6bb17f59d3ea244403592fad33c1c4e865183d1cb8cc908fd7ee
Tx public key: 827326fc771f3674dad46376515b78862630d3dd5b9f15cc7e6504b5d2d8cc25
Timestamp: 1773806413 Timestamp [UTC]: 2026-03-18 04:00:13 Age [y:d:h:m:s]: 00:241:10:44:37
Block: 1500232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177968 RingCT/type: yes/0
Extra: 01827326fc771f3674dad46376515b78862630d3dd5b9f15cc7e6504b5d2d8cc25021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 59bf512c282c299d7a5fc339334330d7860ce4d1bc631e917e33c17054adda4a 0.000600000000 1989902 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": 1500242, "vin": [ { "gen": { "height": 1500232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59bf512c282c299d7a5fc339334330d7860ce4d1bc631e917e33c17054adda4a" } } ], "extra": [ 1, 130, 115, 38, 252, 119, 31, 54, 116, 218, 212, 99, 118, 81, 91, 120, 134, 38, 48, 211, 221, 91, 159, 21, 204, 126, 101, 4, 181, 210, 216, 204, 37, 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: