Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b23ca15ebb13f6f9c3ce01a3c44a56d2882f4eadca9b4383e03d9eba6b6acb1

Tx prefix hash: d2d78d35d102b4f4f8fc4e0658102c74dd529e1a9d741197daba6a208f50373c
Tx public key: 18b0288a8f28e90519f75192ef142f7528519af9357c2be76cd1d10c0609bf98
Timestamp: 1705161942 Timestamp [UTC]: 2024-01-13 16:05:42 Age [y:d:h:m:s]: 02:123:16:32:06
Block: 934527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600438 RingCT/type: yes/0
Extra: 0118b0288a8f28e90519f75192ef142f7528519af9357c2be76cd1d10c0609bf980211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 25b5c5cb5ccb70d9c6d8a15d61b85314ed7d37185052088cfcc04b8b9d83e8f3 0.000600000000 1392541 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": 934537, "vin": [ { "gen": { "height": 934527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25b5c5cb5ccb70d9c6d8a15d61b85314ed7d37185052088cfcc04b8b9d83e8f3" } } ], "extra": [ 1, 24, 176, 40, 138, 143, 40, 233, 5, 25, 247, 81, 146, 239, 20, 47, 117, 40, 81, 154, 249, 53, 124, 43, 231, 108, 209, 209, 12, 6, 9, 191, 152, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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: