Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00dcf09d8f2be254aaebb20ca57c81b51dd701fb9dddc7864b779f704e188bf0

Tx prefix hash: 6e84d511e9c3f5ca8340a47f9adcad29517edc5182f468160d6fc07b5fabefb7
Tx public key: c46ccbdac4dda1edcbc4d1b0f621b0ee5608d84ec0aae771cebe7885697f024c
Timestamp: 1681227133 Timestamp [UTC]: 2023-04-11 15:32:13 Age [y:d:h:m:s]: 03:222:11:30:09
Block: 736348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 945237 RingCT/type: yes/0
Extra: 01c46ccbdac4dda1edcbc4d1b0f621b0ee5608d84ec0aae771cebe7885697f024c0211000000055029cbac000000000000000000

1 output(s) for total of 0.002229326233 xmr

stealth address amount amount idx tag
00: 65bded3ab55d8977c4d133e4a6523bdfa6945975799b3c0b54cb6a2bcc284f61 0.002229326233 1182773 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": 736358, "vin": [ { "gen": { "height": 736348 } } ], "vout": [ { "amount": 2229326233, "target": { "key": "65bded3ab55d8977c4d133e4a6523bdfa6945975799b3c0b54cb6a2bcc284f61" } } ], "extra": [ 1, 196, 108, 203, 218, 196, 221, 161, 237, 203, 196, 209, 176, 246, 33, 176, 238, 86, 8, 216, 78, 192, 170, 231, 113, 206, 190, 120, 133, 105, 127, 2, 76, 2, 17, 0, 0, 0, 5, 80, 41, 203, 172, 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: