Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1c2fc1645f997166e17de413126e9c68e6408df6563d9be3f633d9522aeb455

Tx prefix hash: b7b9a121b2b0f4b6577f3dfd34717adfe98a64e2167939b4114ef3c236dfd4aa
Tx public key: da67466b93ea24660dca2eaa9acf6b4803e9ade019e3b378361cf2697207c9f8
Timestamp: 1744781479 Timestamp [UTC]: 2025-04-16 05:31:19 Age [y:d:h:m:s]: 01:125:09:28:33
Block: 1262497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354332 RingCT/type: yes/0
Extra: 01da67466b93ea24660dca2eaa9acf6b4803e9ade019e3b378361cf2697207c9f8021100000005dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7aa27dafdf3f5d30a19c72c1e4e99352a7b09b24bdd158f48e2a9fcf76733f28 0.000600000000 1749676 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": 1262507, "vin": [ { "gen": { "height": 1262497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aa27dafdf3f5d30a19c72c1e4e99352a7b09b24bdd158f48e2a9fcf76733f28" } } ], "extra": [ 1, 218, 103, 70, 107, 147, 234, 36, 102, 13, 202, 46, 170, 154, 207, 107, 72, 3, 233, 173, 224, 25, 227, 179, 120, 54, 28, 242, 105, 114, 7, 201, 248, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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: