Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc72993f9b4bf8dfb82e7d6b3405b7cb7b9815e014bcb2be4d6f9318448a7496

Tx prefix hash: a241711388d0bc27d58bb76250df12b804d0bb12749fe8f5d91d56a6e3e0e0b9
Tx public key: aac683f1e8297dc3dd04cbd109d3c30f6fce6f65a4c541a81f08303cadbb9baf
Timestamp: 1774504858 Timestamp [UTC]: 2026-03-26 06:00:58 Age [y:d:h:m:s]: 00:236:07:54:27
Block: 1506021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174398 RingCT/type: yes/0
Extra: 01aac683f1e8297dc3dd04cbd109d3c30f6fce6f65a4c541a81f08303cadbb9baf021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8182648f6e83ebbee135b2a53fafc842fe04e7f02bb3feb690bc51f3ca43f96d 0.000600000000 1995763 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": 1506031, "vin": [ { "gen": { "height": 1506021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8182648f6e83ebbee135b2a53fafc842fe04e7f02bb3feb690bc51f3ca43f96d" } } ], "extra": [ 1, 170, 198, 131, 241, 232, 41, 125, 195, 221, 4, 203, 209, 9, 211, 195, 15, 111, 206, 111, 101, 164, 197, 65, 168, 31, 8, 48, 60, 173, 187, 155, 175, 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: