Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de0a037efcb57eee0b4878f5e29f53d6d78fa73eadf681d3d4fb0b4bb846b2df

Tx prefix hash: efb8f3a85f588093015a1c988714ff3e7da4914bddf79f0e7929a0219aa8714d
Tx public key: 8dfb5581c3509ba9d14f5b1011fef555cefd894a34badfb200d9682a58e76f43
Timestamp: 1742008284 Timestamp [UTC]: 2025-03-15 03:11:24 Age [y:d:h:m:s]: 01:252:00:16:18
Block: 1239558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443936 RingCT/type: yes/0
Extra: 018dfb5581c3509ba9d14f5b1011fef555cefd894a34badfb200d9682a58e76f43021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a7f11a60f80cc5e0f97a7d6c55b2491155dc7577b8d107597bb3c0111fa7f78a 0.000600000000 1726523 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": 1239568, "vin": [ { "gen": { "height": 1239558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7f11a60f80cc5e0f97a7d6c55b2491155dc7577b8d107597bb3c0111fa7f78a" } } ], "extra": [ 1, 141, 251, 85, 129, 195, 80, 155, 169, 209, 79, 91, 16, 17, 254, 245, 85, 206, 253, 137, 74, 52, 186, 223, 178, 0, 217, 104, 42, 88, 231, 111, 67, 2, 17, 0, 0, 0, 3, 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: