Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 892aa0f21ca44902f3a5f2bec052ee811be70ab51b436956f618f743de927998

Tx prefix hash: ba62df9991965dea5815151c92d507f6c9c00c0881bc7c1d3cbdd3be51a07bd4
Tx public key: 5a0f7ab3644967d0af76e78982c0975b2b880cae69871b2bdc32d6e5666f7bce
Timestamp: 1745699539 Timestamp [UCT]: 2025-04-26 20:32:19 Age [y:d:h:m:s]: 00:205:18:19:49
Block: 1270107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144768 RingCT/type: yes/0
Extra: 015a0f7ab3644967d0af76e78982c0975b2b880cae69871b2bdc32d6e5666f7bce0211000000062609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44a55c728d7fd98103a92f7ebbc7abceea9c9e96b9bc51ba9610b840d5e225a6 0.600000000000 1757348 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 dinasty-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": 1270117, "vin": [ { "gen": { "height": 1270107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44a55c728d7fd98103a92f7ebbc7abceea9c9e96b9bc51ba9610b840d5e225a6" } } ], "extra": [ 1, 90, 15, 122, 179, 100, 73, 103, 208, 175, 118, 231, 137, 130, 192, 151, 91, 43, 136, 12, 174, 105, 135, 27, 43, 220, 50, 214, 229, 102, 111, 123, 206, 2, 17, 0, 0, 0, 6, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8