Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27fdbd4f25ed1e4fd9b638f7282c8ddc46c515594e73f111f4408dadefae7cd1

Tx prefix hash: 28c941556df4b2c61ae56c5246ae5de52be0e5b40086ce3f42be9678074e6fa8
Tx public key: 4f57a03c8c79ee70fc7a5876847c12f0336ba1d51f639962f953ebc83e2288e4
Timestamp: 1731383740 Timestamp [UCT]: 2024-11-12 03:55:40 Age [y:d:h:m:s]: 00:194:08:29:45
Block: 1151837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138780 RingCT/type: yes/0
Extra: 014f57a03c8c79ee70fc7a5876847c12f0336ba1d51f639962f953ebc83e2288e40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9156a4b24693203241b0dbc9228b7a727302e08475b7782b38d3f140d2799e33 0.600000000000 1637420 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": 1151847, "vin": [ { "gen": { "height": 1151837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9156a4b24693203241b0dbc9228b7a727302e08475b7782b38d3f140d2799e33" } } ], "extra": [ 1, 79, 87, 160, 60, 140, 121, 238, 112, 252, 122, 88, 118, 132, 124, 18, 240, 51, 107, 161, 213, 31, 99, 153, 98, 249, 83, 235, 200, 62, 34, 136, 228, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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