Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71661f0ec55d89ddc6ea830b0ea7b881952978c014dbad888b39f4b77bc69aac

Tx prefix hash: ec4c2908c2d8db6e1faeb3c398b30e4b1ab81500a1b251a078604ff5bbf87cd1
Tx public key: bf9b2b0ac5e85145e5e71ee5a645bd2560a62434a691e70609ba6416d9cde5f0
Timestamp: 1755602050 Timestamp [UTC]: 2025-08-19 11:14:10 Age [y:d:h:m:s]: 01:005:23:36:52
Block: 1349826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270804 RingCT/type: yes/0
Extra: 01bf9b2b0ac5e85145e5e71ee5a645bd2560a62434a691e70609ba6416d9cde5f0021100000005b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aa2f68ed586e7c8683227cfd7233d3db3768b80287cba8ae5e8424b3b82dbafc 0.000600000000 1837761 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": 1349836, "vin": [ { "gen": { "height": 1349826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa2f68ed586e7c8683227cfd7233d3db3768b80287cba8ae5e8424b3b82dbafc" } } ], "extra": [ 1, 191, 155, 43, 10, 197, 232, 81, 69, 229, 231, 30, 229, 166, 69, 189, 37, 96, 166, 36, 52, 166, 145, 231, 6, 9, 186, 100, 22, 217, 205, 229, 240, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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: