Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70bbd43446e16a3b1f96fee7809ee56b6dc776f3041aa18bf7c8408ff0ec8a4a

Tx prefix hash: 9c8b0243db6a60fd3c1c88b70a34b4296734f0c17738b48a596ff79b8f3a0129
Tx public key: 07c1e3ff207afb237d2ad177ae32a0f306ee3f6e34788822d500b7ae258d0339
Timestamp: 1773904618 Timestamp [UTC]: 2026-03-19 07:16:58 Age [y:d:h:m:s]: 00:240:16:45:24
Block: 1501049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177450 RingCT/type: yes/0
Extra: 0107c1e3ff207afb237d2ad177ae32a0f306ee3f6e34788822d500b7ae258d0339021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f9c88a34666a17823b26d020f6742b2b9e32853b8cc5a38962e42c5a37f20052 0.000600000000 1990727 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": 1501059, "vin": [ { "gen": { "height": 1501049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9c88a34666a17823b26d020f6742b2b9e32853b8cc5a38962e42c5a37f20052" } } ], "extra": [ 1, 7, 193, 227, 255, 32, 122, 251, 35, 125, 42, 209, 119, 174, 50, 160, 243, 6, 238, 63, 110, 52, 120, 136, 34, 213, 0, 183, 174, 37, 141, 3, 57, 2, 17, 0, 0, 0, 2, 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: