Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18a6b5b6ef50d351efc4a8761a8d9ce376711777d0c6c683561e2dc5bb9434a3

Tx prefix hash: 6bfccf403953ee2e3e2404655bfd9e8dea636fa17834a5ca6a6ffc91da2d6819
Tx public key: bcf3a633a08369c194c9695570bc2be06a649186174a0c925d21a2b185bfb412
Timestamp: 1699202913 Timestamp [UCT]: 2023-11-05 16:48:33 Age [y:d:h:m:s]: 01:144:08:08:16
Block: 885142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364345 RingCT/type: yes/0
Extra: 01bcf3a633a08369c194c9695570bc2be06a649186174a0c925d21a2b185bfb4120211000000014b8f5122000000000000000000

1 output(s) for total of 0.716402544000 dcy

stealth address amount amount idx
00: 3d41949321964983b564e6e3e1d58a48088bc87320e30e934236f4edab3f084a 0.716402544000 1340897 of 0

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": 885152, "vin": [ { "gen": { "height": 885142 } } ], "vout": [ { "amount": 716402544, "target": { "key": "3d41949321964983b564e6e3e1d58a48088bc87320e30e934236f4edab3f084a" } } ], "extra": [ 1, 188, 243, 166, 51, 160, 131, 105, 193, 148, 201, 105, 85, 112, 188, 43, 224, 106, 100, 145, 134, 23, 74, 12, 146, 93, 33, 162, 177, 133, 191, 180, 18, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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