Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a1c1301dd4e7d93a8ed208bf152cbc7b1049e4491375418172dfef603faf788

Tx prefix hash: ddf6e53555b25a50121fef2b0e812a9474e7a3f7ae3a11d456830eb33af8705f
Tx public key: d03adc66e9c55cce5790f8d69bcf8465034219cc3db3ae0d94c40f655cfa3c16
Timestamp: 1734909272 Timestamp [UCT]: 2024-12-22 23:14:32 Age [y:d:h:m:s]: 00:100:17:59:27
Block: 1181072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71760 RingCT/type: yes/0
Extra: 01d03adc66e9c55cce5790f8d69bcf8465034219cc3db3ae0d94c40f655cfa3c160211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27cb10e2a444b307dc0c2f35306861bfe08d1b4e39f818410b96a4d26feae0bf 0.600000000000 1667487 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": 1181082, "vin": [ { "gen": { "height": 1181072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27cb10e2a444b307dc0c2f35306861bfe08d1b4e39f818410b96a4d26feae0bf" } } ], "extra": [ 1, 208, 58, 220, 102, 233, 197, 92, 206, 87, 144, 248, 214, 155, 207, 132, 101, 3, 66, 25, 204, 61, 179, 174, 13, 148, 196, 15, 101, 92, 250, 60, 22, 2, 17, 0, 0, 0, 2, 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