Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d3e5b9b7e2926186cf52b62e5b527d658f7fa777aa6cec09e3be7151b921186

Tx prefix hash: f0ed16dfc37548bf687d3a4f28d89a542f611d016f529e18e431c4a14e065139
Tx public key: eb76bde46e5eb396cd9b36c242e45ed7e1e1cdff91bc133f8db0ef3ca0004758
Timestamp: 1736716740 Timestamp [UTC]: 2025-01-12 21:19:00 Age [y:d:h:m:s]: 01:312:08:52:23
Block: 1195995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487220 RingCT/type: yes/0
Extra: 01eb76bde46e5eb396cd9b36c242e45ed7e1e1cdff91bc133f8db0ef3ca0004758021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3217bd9e478f031c7bef3b3c1df0e32f1e6cf7622fcfa83343abc48b1b34389a 0.000600000000 1682592 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": 1196005, "vin": [ { "gen": { "height": 1195995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3217bd9e478f031c7bef3b3c1df0e32f1e6cf7622fcfa83343abc48b1b34389a" } } ], "extra": [ 1, 235, 118, 189, 228, 110, 94, 179, 150, 205, 155, 54, 194, 66, 228, 94, 215, 225, 225, 205, 255, 145, 188, 19, 63, 141, 176, 239, 60, 160, 0, 71, 88, 2, 17, 0, 0, 0, 2, 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: