Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b4e2a94312ccb5da15b90d67d26e95b03e115e4b96d125c0a19b7f54726b98a

Tx prefix hash: c0ebc43f2a32ea65d92dff5aa530b9863e1523955a7539707e6032991129a1e1
Tx public key: be137377ed41e04f21cd3fdc0725947a0d403fcdfc03cc925855f87a41f484b5
Timestamp: 1780096373 Timestamp [UTC]: 2026-05-29 23:12:53 Age [y:d:h:m:s]: 00:169:07:31:30
Block: 1546453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 132257 RingCT/type: yes/0
Extra: 01be137377ed41e04f21cd3fdc0725947a0d403fcdfc03cc925855f87a41f484b5

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1d0e35c5772fa2728bc79f6e9184e9e82112362436d479ec9202a40a9ec8679e 0.000600000000 2036427 of 15 <6e>

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": 1546463, "vin": [ { "gen": { "height": 1546453 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "1d0e35c5772fa2728bc79f6e9184e9e82112362436d479ec9202a40a9ec8679e", "view_tag": "6e" } } } ], "extra": [ 1, 190, 19, 115, 119, 237, 65, 224, 79, 33, 205, 63, 220, 7, 37, 148, 122, 13, 64, 63, 205, 252, 3, 204, 146, 88, 85, 248, 122, 65, 244, 132, 181 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: