Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57324273d8543c351f98b7a8a91b9b895102d4eee4b5d1fd176304579b522269

Tx prefix hash: 5bb335286a6e9d3d5eb94cb99e7a29f4c30314cd79a5021fb56196a936ef44c2
Tx public key: 1e33512a0fbc5ad91c19bc043ff7d1030364ba4da80088778d70455a2d7c656e
Timestamp: 1706240074 Timestamp [UCT]: 2024-01-26 03:34:34 Age [y:d:h:m:s]: 00:355:18:24:39
Block: 943450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254711 RingCT/type: yes/0
Extra: 011e33512a0fbc5ad91c19bc043ff7d1030364ba4da80088778d70455a2d7c656e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ababff9b695423c9b7f718549d41895a6b9e93d9b4489d6611ac49a001ec7c62 0.600000000000 1401656 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": 943460, "vin": [ { "gen": { "height": 943450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ababff9b695423c9b7f718549d41895a6b9e93d9b4489d6611ac49a001ec7c62" } } ], "extra": [ 1, 30, 51, 81, 42, 15, 188, 90, 217, 28, 25, 188, 4, 63, 247, 209, 3, 3, 100, 186, 77, 168, 0, 136, 119, 141, 112, 69, 90, 45, 124, 101, 110, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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