Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b49a62e906eeeb9fa2866c5bfee8d693909bff6e9f941da19746c1ae6beb2b9

Tx prefix hash: 7b0d80b04b4c83639237a2ce7f49eb681f365d817369bd7057e9f00354e9ec05
Tx public key: 0333240e2ddc65c3baa3d29ad416704f9f17286d6b6ffab196d38d06b29032c7
Timestamp: 1774656706 Timestamp [UTC]: 2026-03-28 00:11:46 Age [y:d:h:m:s]: 00:045:06:27:02
Block: 1507277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24630 RingCT/type: yes/0
Extra: 010333240e2ddc65c3baa3d29ad416704f9f17286d6b6ffab196d38d06b29032c7021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 40d09293d75c5c80b0a2de3be01d40eb18b93a97f654e2e7f873642bcd57acd7 0.000600000000 1997029 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": 1507287, "vin": [ { "gen": { "height": 1507277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40d09293d75c5c80b0a2de3be01d40eb18b93a97f654e2e7f873642bcd57acd7" } } ], "extra": [ 1, 3, 51, 36, 14, 45, 220, 101, 195, 186, 163, 210, 154, 212, 22, 112, 79, 159, 23, 40, 109, 107, 111, 250, 177, 150, 211, 141, 6, 178, 144, 50, 199, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: