Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 693c61fc79923c1148b1da979e3cfe337a7116976ce8e1b87ccee80c4874baa7

Tx prefix hash: ca01b182041bb047f2d39a4c08fd35851393f4eb1096e2d921d4ed70dcda84c1
Tx public key: 65aebd84cc0a8a4aa09d7577c4cffdc7e33797f16313b0ffbd1626368863049e
Timestamp: 1731809979 Timestamp [UCT]: 2024-11-17 02:19:39 Age [y:d:h:m:s]: 00:139:17:08:02
Block: 1155361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99681 RingCT/type: yes/0
Extra: 0165aebd84cc0a8a4aa09d7577c4cffdc7e33797f16313b0ffbd1626368863049e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc29f23788d56e2d45ae3052ca5f7a7cd3c3c146170adb60c964047c3eadda46 0.600000000000 1640976 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": 1155371, "vin": [ { "gen": { "height": 1155361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc29f23788d56e2d45ae3052ca5f7a7cd3c3c146170adb60c964047c3eadda46" } } ], "extra": [ 1, 101, 174, 189, 132, 204, 10, 138, 74, 160, 157, 117, 119, 196, 207, 253, 199, 227, 55, 151, 241, 99, 19, 176, 255, 189, 22, 38, 54, 136, 99, 4, 158, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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