Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aca7539dc79b449f18788ebea5cfc6673fc048bee915100cb10fef894a184fa1

Tx prefix hash: 9490bd6933796f5a4c85b51229e14bbefa60f2e1919edd14de3aa6255a24c20d
Tx public key: 63b0934fb3eeb329f21f5de021dce7ce5aa483a94d5001900f9295062e55f193
Timestamp: 1745234943 Timestamp [UTC]: 2025-04-21 11:29:03 Age [y:d:h:m:s]: 01:212:03:42:41
Block: 1266243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415726 RingCT/type: yes/0
Extra: 0163b0934fb3eeb329f21f5de021dce7ce5aa483a94d5001900f9295062e55f1930211000000016c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4ddd8ee3621d7c8eed32a5214ff22f81040ff9b16482ae3d193a975857b1de1d 0.000600000000 1753464 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": 1266253, "vin": [ { "gen": { "height": 1266243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ddd8ee3621d7c8eed32a5214ff22f81040ff9b16482ae3d193a975857b1de1d" } } ], "extra": [ 1, 99, 176, 147, 79, 179, 238, 179, 41, 242, 31, 93, 224, 33, 220, 231, 206, 90, 164, 131, 169, 77, 80, 1, 144, 15, 146, 149, 6, 46, 85, 241, 147, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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: