Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3e064d09e2054df75133847583641a2b6ec0be09b07f4fc67e4a09244618eb2

Tx prefix hash: 31b2c7be0461e1d30fcbe300138b1f0e9060d2964c7b9d85f6a5a8ccc60a4822
Tx public key: 345a98937910c6f2c305ad0d288cc61b69aeaa57e92815ce46523eaec7eef591
Timestamp: 1717413040 Timestamp [UTC]: 2024-06-03 11:10:40 Age [y:d:h:m:s]: 02:168:23:01:36
Block: 1036119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645691 RingCT/type: yes/0
Extra: 01345a98937910c6f2c305ad0d288cc61b69aeaa57e92815ce46523eaec7eef5910211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d94c8f39f4fb3cf30c884d5790e711c1a3c34f22e81da636b39af729727d9f26 0.000600000000 1504644 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": 1036129, "vin": [ { "gen": { "height": 1036119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d94c8f39f4fb3cf30c884d5790e711c1a3c34f22e81da636b39af729727d9f26" } } ], "extra": [ 1, 52, 90, 152, 147, 121, 16, 198, 242, 195, 5, 173, 13, 40, 140, 198, 27, 105, 174, 170, 87, 233, 40, 21, 206, 70, 82, 62, 174, 199, 238, 245, 145, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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: