Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66982f1e1be6d0d3eb416fc07858bd418de4fe2cab8390a4a751feba29cb470a

Tx prefix hash: 8d41795d588e39929440c2adcffc185007c4ddf3b0f2b513372fae1f3f503e94
Tx public key: c432f15519ff2d451a0baf68b9fed26d70e27c15ea74294a07905a6e456e24cb
Timestamp: 1737865510 Timestamp [UTC]: 2025-01-26 04:25:10 Age [y:d:h:m:s]: 01:294:07:39:25
Block: 1205462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474177 RingCT/type: yes/0
Extra: 01c432f15519ff2d451a0baf68b9fed26d70e27c15ea74294a07905a6e456e24cb021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 56c214e559b7d6a562266d389c208bd430daf28fb52f9c710d9ced8c2686b2ba 0.000600000000 1692159 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": 1205472, "vin": [ { "gen": { "height": 1205462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56c214e559b7d6a562266d389c208bd430daf28fb52f9c710d9ced8c2686b2ba" } } ], "extra": [ 1, 196, 50, 241, 85, 25, 255, 45, 69, 26, 11, 175, 104, 185, 254, 210, 109, 112, 226, 124, 21, 234, 116, 41, 74, 7, 144, 90, 110, 69, 110, 36, 203, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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: