Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cc53be114b10e9ef5bb147c7acb36dec017356030a91e2740cba23a5ffe378d

Tx prefix hash: 5252e6256b9c9a8f7243e74def62dc7be6b705b4a7ddb1bf26acd405ccbba330
Tx public key: 2d8027abd895f5dc516bde8c899ad67623c92229e2acfdac84b4cd985374be4e
Timestamp: 1713091235 Timestamp [UTC]: 2024-04-14 10:40:35 Age [y:d:h:m:s]: 02:221:15:36:48
Block: 1000264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 683230 RingCT/type: yes/0
Extra: 012d8027abd895f5dc516bde8c899ad67623c92229e2acfdac84b4cd985374be4e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a6f0c8e042a3bd7f62f36cd63a30583df6d834535282b58eb4b596d91229c14d 0.000600000000 1460760 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": 1000274, "vin": [ { "gen": { "height": 1000264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6f0c8e042a3bd7f62f36cd63a30583df6d834535282b58eb4b596d91229c14d" } } ], "extra": [ 1, 45, 128, 39, 171, 216, 149, 245, 220, 81, 107, 222, 140, 137, 154, 214, 118, 35, 201, 34, 41, 226, 172, 253, 172, 132, 180, 205, 152, 83, 116, 190, 78, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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: