Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27ce97cd189a40d8e6d53312f12405772e6370719f49233b9b973308c3806d89

Tx prefix hash: 3d0904b545efb9240f406422e556cfd2e586f87f3f8ad27e641b2329145b6075
Tx public key: 981b532baa1bc09a7a99596c701558d9b75315362d537f3f9cfa429dc5b880ab
Timestamp: 1731981657 Timestamp [UTC]: 2024-11-19 02:00:57 Age [y:d:h:m:s]: 01:290:07:46:47
Block: 1156797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471864 RingCT/type: yes/0
Extra: 01981b532baa1bc09a7a99596c701558d9b75315362d537f3f9cfa429dc5b880ab021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a6788595f1a8ad9594d5374f89e50d82e40eb2fb585d17ca8922d74ca0f3326 0.000600000000 1642420 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": 1156807, "vin": [ { "gen": { "height": 1156797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6788595f1a8ad9594d5374f89e50d82e40eb2fb585d17ca8922d74ca0f3326" } } ], "extra": [ 1, 152, 27, 83, 43, 170, 27, 192, 154, 122, 153, 89, 108, 112, 21, 88, 217, 183, 83, 21, 54, 45, 83, 127, 63, 156, 250, 66, 157, 197, 184, 128, 171, 2, 17, 0, 0, 0, 1, 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: