Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c28df8b2e4c5a109c79e3d9c668dc7f4657af585417add43af78745b882b452c

Tx prefix hash: 0c8cd18b80a2bb0397f5575d4c6192fff88fad4b31ef87d6960ae709fbf2b51c
Tx public key: 2d0fd15629cfb0f76537720bf3fa04212f7bcd23f5a7ae6cc67cc409d16b549c
Timestamp: 1650398361 Timestamp [UTC]: 2022-04-19 19:59:21 Age [y:d:h:m:s]: 04:131:19:40:21
Block: 483779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1139197 RingCT/type: yes/0
Extra: 012d0fd15629cfb0f76537720bf3fa04212f7bcd23f5a7ae6cc67cc409d16b549c02110000000f2e6b1fd5000000000000000000

1 output(s) for total of 0.015312269918 xmr

stealth address amount amount idx tag
00: 5616a4a16b473ce97e355fa6dac71326226ff4afaff5268fdd033c3004b42717 0.015312269918 905524 of 0 -

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": 483789, "vin": [ { "gen": { "height": 483779 } } ], "vout": [ { "amount": 15312269918, "target": { "key": "5616a4a16b473ce97e355fa6dac71326226ff4afaff5268fdd033c3004b42717" } } ], "extra": [ 1, 45, 15, 209, 86, 41, 207, 176, 247, 101, 55, 114, 11, 243, 250, 4, 33, 47, 123, 205, 35, 245, 167, 174, 108, 198, 124, 196, 9, 209, 107, 84, 156, 2, 17, 0, 0, 0, 15, 46, 107, 31, 213, 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: